Turbo decoder with reduced-size branch metric cache

ABSTRACT

A method and an apparatus for producing branch metrics in a LogMAP turbo decoding operation. During a forward recursion of a trellis, a set of primary branch metrics is generated. The primary branch metrics are stored in receiver form in a relatively small memory cache module ( 370 ) and corresponding secondary branch metrics are produced by negating the primary branch metrics. The primary branch metrics and said secondary branch metrics constitute all possible branch metrics for a given state in the trellis. During a backwards recursion of the trellis, the stored primary branch metrics are retrieved from the memory cache module ( 370 ) and the secondary branch metrics are regenerated by negating the retrieved primary branch metrics.

CROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims priority of Australian Provisional Application No. PR6793, which filed on Aug. 3, 2001.

BACKGROUND OF THE INVENTION

[0002] I. Field of the Invention

[0003] The present invention relates generally to decoding in communication systems and, in particular, to the calculation of branch metrics in logMAP turbo decoding in wireless communication systems.

[0004] II. Description of the Related Art

[0005] Turbo decoding utilizes interactive decoding and random interleaving to achieve an error performance close to the Shannon limit Consequently, turbo decoding is often employed in decoding for third generation (3G) wireless communications systems.

[0006] A trellis diagram represents the possible state changes of a convolutional encoder over time. Each state in the trellis is connected, via two associated branch metrics, to two separate states in the trellis in the next time period. When decoding received symbols, decoding algorithms typically traverse the trellis in a forward direction to determine the probabilities of the individual states and the associated branch metrics.

[0007] The logMAP algorithm differs from other decoding algorithms, such as the Viterbi algorithm, by performing both a forward and a backward recursion over a trellis. The algorithm can be partitioned to provide a Windowed LogMAP arrangement where the blocks are divided into smaller alpha and beta recursions. Alpha values, representing the probabilities of each state in the trellis, are determined in the forward recursion. Beta values, representing the probabilities of each state in the reverse direction, are determined during the backwards recursion.

[0008] The respective probabilities of each pair of branch metrics associated with any given state are the gamma values (γ). The gamma values are calculated during each of the forward and backwards recursions of the trellis. The logMAP branch metrics are calculated using the following equation:

γ_(k) ¹ =d ¹(y _(s) +Le)+y _(p) c ^(1,k)  (1)

[0009] where i represents the path (0 or 1), d and c are the expected data and parity bits, respectively, and y_(s), y_(p) and L_(e) represent the soft information for data, parity and extrinsic information, respectively, and k represents the current state in the trellis for which branch metrics are being calculated.

[0010] For any given rate 1/2 trellis code, each of the expected data and parity bits, d and c respectively, may take the values of +1 or −1. Consequently, there are four possible branch metric combinations for the given input variables:

[0011] (y_(s)+L_(e)+y_(p)) for d=+1, c=+1;

[0012] (y_(s)+L_(e)+y_(p)) for d=+1, c=−1;

[0013] (−y_(s)−L_(e)−y_(p)) for d=−1, c=−1;

[0014] (−y_(s)−L_(e)+y_(p)) for d=−1, c=+1.

[0015] When traversing the trellis in the forward recursion stage, both the input symbol and the extrinsic memory must be accessed to compute the gamma values. FIG. 1 shows a prior art arrangement 100 for calculating branch metrics for a rate 1/2 decoder. Data (y_(s)) 130 and parity (y_(p)) 140 are read from a first memory 120. The time and power required for read accesses from the first memory 120 are proportional to the size of the first memory 120. The first memory 120 must be sufficiently large to store data and parity information for the entire length of the block being decoded. The first memory 120 is typically of the order of −5 k words in size for mobile communications applications.

[0016] It is possible to store the data 130 and parity 140 in two distinct memory units, rather than the single first memory 120. However, there does not appear to be any apparent advantage associated with such an implementation, as reading the required data 130 and parity 140 from separate memory units would require two memory address decodes in addition to the retrieval of the information. Such an implementation is not appreciably faster than a single memory unit implementation and requires more power.

[0017] A processor 150 receives the data 130 and parity 140, along with extrinsic information (L_(e)) 115 that is read from a second memory 110, to produce output branch metrics 155 corresponding to all paths in the trellis. The output branch metric 155 is presented to a trellis calculation module 160 that utilizes the output branch metric 155 to traverse the trellis.

[0018] When the backward recursion of the trellis commences to calculate the beta values, each of the four possible combinations for the branch metric computation must be regenerated. This requires a read access to the memory 120 storing data and parity information, and one read access to the second memory 110 storing extrinsic information, in addition to the cost of computation in the processor 150. As noted above, the time and power consumption of each memory access is directly proportional to the number of memory cells and, consequently, each read access to either one of the first memory 120 and the second memory 110 is costly with respect to power consumption Therefore, reducing the number of read accesses to either one or both of the first memory 120 and the second memory 110 would be advantageous.

[0019]FIG. 2 shows a prior art arrangement 200 for calculating branch metrics for a rate 1/3 LogMAP decoder. The branch metric combinations are given by Equation 2 below, in which y_(p1) represents a first parity bit, y_(p2) represents a second parity bit, c₁ represents the expected first parity bit and c₂ represents the expected second parity bit

γ_(k) ¹ =d ¹(y _(a) +Le)+y _(p1) c ₁ ^(1,k) +y _(p2) c ₂ ^(1,k)  (2)

[0020] As each of d, c₁ and c₂ can be either +1 or −1, there are eight possible branch metric combinations for a rate 1/3 decoder.

[0021] A first memory 220 stores each of data (y_(s)) 230, first parity (y_(p1)) 240 and second parity (y_(p2)) 245. Each of the data (y_(s)) 230, first parity (y_(p1)) 240 and second parity (y_(p2)) 245 is read from the first memory 220 and presented to a processor 250. The processor 250 also receives extrinsic information (L_(e)) 215 that is read from a second memory 210. The processor 250 calculates all the branch metrics 255, and presents the branch metrics 255 to a trellis calculation module 260.

[0022] Branch metrics calculated during the forward recursion of a decoding trellis are often stored in memory units so that the branch metrics can be reused during a backwards recursion of the decoding trellis. As all of the branch metrics calculated during the forward recursion are stored, the memory units utilized are necessarily large. As noted above, read accesses to such memory units are costly in respect of power consumption and time.

[0023] In UMTS and CDMA 2000 systems, approximately 40% of computation in baseband processing is in the turbo decoding process alone. A single component can dominate the power consumption of a low-power handset, or a large infrastructure product. Any amount of power savings translates into a substantial advantage in the handset market, where battery life is paramount, or in packaging for wireless infrastructure products, where heat dissipation is important

SUMMARY OF THE INVENTION

[0024] The present invention provides a method for generating at least two branch metrics. The method generates the branch metrics, each having an inverse polarity to the other.

[0025] In one embodiment of the present invention, at least one primary branch metric and at least one secondary branch metric are generated. The secondary branch metric is generated by negating the primary branch metric.

[0026] In one example of the present invention, a method provides for producing branch metrics in a LogMAP turbo decoding operation. The method comprises generating a branch metric for each primary combination of extrinsic, parity and information data, and storing the primary branch metrics to generate by negation the remaining secondary ones of the branch metrics, during a forward recursion of a trellis. During a backwards recursion of the trellis, the method comprises retrieving the stored primary branch metrics, and generating the secondary branch metrics by negating the retrieved primary branch metrics.

[0027] Other aspects of the present invention are also disclosed.

BRIEF DESCRIPTION OF THE DRAWINGS

[0028] The present invention will be better understood from reading the following description of non-limiting embodiments, with reference to the attached drawings, wherein below:

[0029]FIG. 1 is a block diagram representation of a known arrangement for calculating branch metrics for a rate 1/2 decoder;

[0030]FIG. 2 is a block diagram representation of a known arrangement for calculating branch metrics for a rate 1/3 decoder;

[0031]FIG. 3 is a schematic block diagram representation of an arrangement for a rate 1/2 logMAP turbo decoder that utilizes a branch metric cache; and

[0032]FIG. 4 is a schematic block diagram representation of an arrangement for a rate 1/5 logMAP turbo decoder that utilizes a branch metric cache.

[0033] It should be emphasized that the drawings of the instant application are not to scale but are merely schematic representations, and thus are not intended to portray the specific dimensions of the invention, which may be determined by skilled artisans through examination of the disclosure herein.

DETAILED DESCRIPTION

[0034] Where reference is made in any one or more of the accompanying drawings to steps and/or features, which have the same reference numerals, those steps and/or features have for the purposes of this description the same function(s) or operation(s), unless the contrary intention appears.

[0035]FIG. 3 shows an arrangement 300 for rate 1/2 LogMAP turbo decoding that utilizes a branch metric cache 370. During a forward recursion of a coding trellis, a read access from a first memory 320 is required to access data (y_(s)) 330 and parity (y_(p)) 340, each typically described by 8 bits of information. Extrinsic information 315 is read from a second memory 310. The memories 310 and 320 typically have a capacity of 5 kilobytes for mobile implementations. Each of the retrieved data 330, parity 340 and extrinsic information 315 is presented to a first processor 350. The first processor 350 calculates from the retrieved parity, extrinsic and information data, a predetermined half of the relevant combinations of the data, thus providing a set of primary branch metrics 355. The set 355 is stored in the cache memory 370 and is also provided to each of a trellis calculation module 360 and a second processor 390. The second processor 390 negates the set of primary branch metrics 355 to produce a set of secondary branch metrics 395, which are provided to the trellis calculation module 360.

[0036] Due to the symmetry of a trellis structure, for a rate 1/2 trellis decoder two of the four possible branch metric combinations may be generated from the other two possible combinations. Thus, (y_(s)+L_(e)+y_(p)) and (y_(s)+L_(e)−y_(p)) can be negated to produce (−y_(s)−L_(e)−y_(p)) and (−y_(s)−L_(e)+y_(p)), respectively. The branch metric combinations that are calculated are the primary branch metrics. The corresponding branch metric combinations that are derived by negating the primary branch metric combinations are the secondary branch metric combinations. Due to the storage of the set of primary branch metrics in the cache memory 370, it is only necessary to access data and parity and the corresponding extrinsic information from the two memory units 310 and 320, during the forward recursion of a trellis. The remaining two branch metrics are calculated by negating the first two calculated branch metrics. The negation is relatively inexpensive, both in terms of processing time and power consumption and is performed by the second processor 390. All possible branch metric combinations are presented to the trellis calculation module 360 in the forward recursion to determine the alpha values.

[0037] As two of the branch metrics may be generated by negating the first two branch metrics, only the first two calculated branch metrics are stored in the branch metric cache 370. Accordingly, the size of the branch metric cache need only be sufficiently large to store half of the possible set of branch metrics and thus the cache may be referred to as a reduced set branch metric cache.

[0038] When the backward recursion of the trellis commences to calculate required beta values, the trellis processor 360 sends a control signal 365 to retrieve from the reduced set branch metric cache 370 the primary branch metrics 355 that were stored during the forward trellis recursion, thus obviating memory accesses to each of the first memory 320 and the second memory 310. Due to the relatively small size of the reduced set branch metric cache 370, typically about the window size, any read access to retrieve required primary branch metrics from the reduced set branch metric cache 370 requires significantly less time and power than a comparable read access from either one of the first memory 320 and the second memory 310. Furthermore, retrieving primary branch metrics 355 directly from the reduced set branch metric cache 370 allows the backward recursion of the trellis to omit calculations undertaken during the forward trellis traversal by the processor 350. Thus, utilizing a reduced set branch metric cache 370 that is relatively small provides desirable time and power savings over prior art arrangements. The retrieved primary branch metrics 380 are presented to each of the trellis calculation module 360 and the second processor 390. Negation of the retrieved primary branch metrics 380 is again performed by the second processor 390 to produce secondary branch metrics 385 to complete the set of branch metrics necessary for trellis calculation.

[0039] As the reduced set branch metric cache 370 is only required to store half of the possible branch metric combinations generated during the forward recursion of a decoding trellis, the reduced set branch metric cache 370 may be implemented using a small, dedicated memory unit The power consumption associated with a read access to any memory unit is dependent on the size of the memory unit being accessed. As the reduced set branch metric cache 370 is significantly smaller than memory units required to store all branch metric combinations calculated during a forward recursion of a decoding trellis, read accesses to the reduced set branch metric cache 370 are quicker and consume less power.

[0040]FIG. 4 shows an arrangement 400 for logMAP decoding for a rate 1/3 decoder. During a forward recursion of a coding trellis, data (y_(s)) 430, first parity (y_(p1)) 440 and second parity (y_(p2)) 445 are obtained via read accesses from a first memory 420. Extrinsic information (L_(e)) 415 is obtained via a read access from a second memory 410. Each of the data (y_(s)) 430, first parity (y_(p1)) 440, second parity (y_(p2)) 445 and extrinsic information (L_(e)) 415 are presented to a first processor 450. The first processor 450 produces four branch metric possibilities 455 from the input parameters and presents the branch metrics 455 to each of a reduced set branch metric cache 470, a second processor 490 and a trellis calculation module 460. Each of the branch metrics 455 is stored in the reduced set branch metric cache 470. The remaining four possible combinations are then generated by the second processor 490 by negating the initial four branch metric combinations 455 to produce a secondary set of branch metrics 495, which are presented to the trellis calculation module 460.

[0041] During a backwards recursion of a trellis, the trellis calculation module 460 retrieves branch metrics 455 from the reduced set branch metric cache 470 without the need to recalculate the branch metrics, thus realizing significant power and time savings. The trellis calculation module sends a control signal 465 to the reduced set branch metric cache 470. The branch metrics 455 that were stored during the forward recursion of the trellis are accessed and presented as retrieved branch metrics 480 to each of the trellis calculation module 460 and the second processor 490. The second processor 490 negates the retrieved branch metrics 480 to generate secondary branch metrics 485 that are presented to the trellis calculation module 460 to complete the set of branch metrics necessary for trellis calculation.

[0042] Whilst a branch metric cache for a rate 1/3 decoding application is required to store more information than a branch metric cache for a rate 1/2 decoding application, and therefore must be larger in size, the memory units utilized in the rate 1/3 decoding application must be correspondingly larger than the memory units utilized in the rate 1/2 decoding. Consequently, the principle of utilizing a relatively small, dedicated branch metric cache may be extended to any combination of decoding rates.

[0043] The principles of the methods and arrangements described herein have general applicability to trellis decoding in telecommunications systems.

[0044] While the particular invention has been described with reference to illustrative embodiments, this description is not meant to be construed in a limiting sense. It is understood that although the present invention has been described, various modifications of the illustrative embodiments, as well as additional embodiments of the invention, will be apparent to one of ordinary skill in the art upon reference to this description without departing from the spirit of the invention, as recited in the claims appended hereto. Consequently, the method, system and portions thereof and of the described method and system may be implemented in different locations, such as a wireless unit, a base station, a base station controller, a mobile switching center and/or a radar system. Moreover, processing circuitry required to implement and use the described system may be implemented in application specific integrated circuits, software-driven processing circuitry, firmware, programmable logic devices, hardware, discrete components or arrangements of the above components as would be understood by one of ordinary skill in the art with the benefit of this disclosure. Those skilled in the art will readily recognize that these and various other modifications, arrangements and methods can be made to the present invention without strictly following the exemplary applications illustrated and described herein and without departing from the spirit and scope of the present invention It is therefore contemplated that the appended claims will cover any such modifications or embodiments as fall within the true scope of the invention. 

We claim:
 1. A method of decoding comprising: generating at least two branch metrics for a primary combination of extrinsic, parity and information data during at least a forward recursion, wherein one of the at least two branch metrics has an inverse polarity to another of the at least two branch metrics.
 2. The method of claim 1, further comprising: generating secondary branch metrics from the generated at least two branch metrics during at least a backwards recursion.
 3. The method of claim 2, further comprising: storing the branch metrics generated for the primary combination to generate the secondary branch metrics corresponding thereto.
 4. The method of claim 3, wherein the secondary branch metrics are the negation of the corresponding stored branch metrics generated for the primary combination.
 5. The method of claim 4, wherein the step of generating the secondary branch metrics comprises: retrieving the stored branch metrics generated for the primary combination during at least a backwards recursion.
 6. The method of claim 5, wherein the step of generating secondary branch metrics comprises: negating the retrieved branch metrics generated for the primary combination.
 7. The method of claim 6, wherein the forward recursion and the backwards recursion are part of a trellis algorithm.
 8. A method for producing branch metrics comprising: generating at least one primary branch metric; and generating at least one secondary branch metric by negating the primary branch metric.
 9. The method of claim 8, wherein the primary branch metrics are generated from data, parity information and extrinsic information.
 10. The method of claim 9, wherein the branch metrics are employed in a LogMAP decoding and/or a turbo decoding operation.
 11. A decoder comprising: a first processing unit for generating at least one primary branch metric; and a second processing unit for generating at least one secondary branch metric by negating the primary branch metric.
 12. The decoder of claim 11, further comprising: at least one store for retaining data, parity information and extrinsic information; the first processing unit for retrieving the data, the parity information and the extrinsic information from the at least one store, and for generating the at least one primary branch metric in a forward recursion of a trellis; a memory cache module for storing the at least one primary branch metric in the forward recursion; and a trellis calculator for receiving the at least one primary branch metric and the corresponding secondary branch metrics from the second processor, and for decoding the trellis in the forward recursion.
 13. The decoder of claim 12, wherein the trellis calculation module for retrieving the at least one primary branch metric from the memory cache module and the corresponding secondary branch metrics from the second processing unit, and for decoding the trellis in a backwards recursion direction.
 14. The decoder of claim 13, the decoder implemented in a device selected from the group consisting of: a mobile telephone handset; a cellular base station; a telecommunications satellite; and a microwave base station.
 15. The decoder of claim 13, the decoder implemented in a LogMAP decoder and/or a turbo decoder. 